Working on a file in KS 2025.2 [4.12.157] and today when I opened it, I get hit with the following errors: I’ve attached the latest log file as a .txt in case it helps.
Would love to know what’s going on here because I can’t enter GPU mode in this file. I don’t have any other versions of this file, so I’d hate for it to be corrupted.
Does the rescue mode open the file without this error?
Move or delete the “optix7cache.db” from ressources folder, does the error appear?
Hope the devs can solve this ticket.
This worked. Thanks for the suggestion.
But… why? Is this a matter of a cache not clearing automatically after a problem was resolved? Would love to know more if you are able to share.
These were just guesses from me.
Does the rescue mode opens the scene without issues?
Or was it moving / deleting optix7cache.db?
The comment with the ticket for the devs was just a hint or better a question, if you created one?
I have no further infos to share.
But, cool for other users, if have similar issues. And hopefully KeyShot will read this post.
Deleting optix7cache.db is all I did. I relaunched the scene and had no further issues.
I didn’t create an official ticket for this since I didn’t know the cause or if it was not a bug but user error on my part.
Great to hear deleting the optix cache has fixed this issue. I will still ask a developer to look at this and hopefully understand how that god corrupted in the first place!
Not sure if this is related? But I’m getting this message when trying to open a new scene turning GPU mode on. GPU is extremely slow to load.
Keyshot 2025.2 4.14.157
Tried the optix delete but got the same error with more errors.
@Billy.Bagel that’s actually a bug ( GPU startup error - #14 by jan.simon.1 - Help and Troubleshooting - Luminaries ) and only happens in an empty scene.
Even when you switch to GPU before you switch the lighting mode it doesn’t happen. If you GPU most of the time you can also change the default scene so it will start already in GPU mode and you don’t have to switch every time.
Thank you Oscar! In my case, it seems like the order of operations doesn’t matter, I still get the error. What seems to have worked is adding geometry before turning GPU or product Mode on. So I saved that as my startup for now. It will just startup with a basic cube, lol.
